This won't work in my opinion. You may be providing the path, but it would still load all the migrations path.

I have tested this change and it indeed works with 5.3.x as the Illuminate\Database\Console\Migrations\BaseCommand respects the path option (if present) in the getMigrationPaths method. With this change in place, when I run migrate:rollback and specify a --path=database/migrations/tenant option it only attempts to rollback the migrations in the tenant subfolder and doesn't attempt to rollback the migrations in the main migrations folder.

Let me know if you have any questions.

Also doesn't work --path option in migrate:refresh and migrate:reset

@afigienas looks like the RefreshCommand has the path option but the ResetCommand doesn't.

@anderly but looks like $path variable are not sent to rollback or reset command.

https://github.com/laravel/framework/blob/5.3/src/Illuminate/Database/Console/Migrations/RefreshCommand.php

        if ($step > 0) {
            $this->call('migrate:rollback', [
                '--database' => $database, '--force' => $force, '--step' => $step,
            ]);
        } else {
            $this->call('migrate:reset', [
                '--database' => $database, '--force' => $force,
            ]);
        }

it is used only in

  $this->call('migrate', [
            '--database' => $database,
            '--force' => $force,
            '--path' => $path,
        ]);

so the error comes in "clear DB" step

@afigienas oh, you're right! I only saw that the path option was defined.

Ok, so looks like the RefreshCommand and ResetCommand should respect and send the --path option when fired as well for this to be a complete patch.

I'll add those changes to this PR.

Updated RefreshCommand and ResetCommand, updated tests and squashed commits. Should be ready to go.